I learned from @pi0 in #13513 that import.meta.resolve no longer takes a second argument, meaning it can't be used for resolving a peer dependency relative to the current working directory. As such, we won't be able to migrate to it once it's supported everywhere we care about.

So unless we intend to keep import-meta-resolve around forever, we should just get rid of it now. I don't think we need to use a library for this (especially since we know which packages we're using this with, and so don't need to deal with any weird edge cases) — we can just implement the logic ourselves. This PR adds a resolve_peer function which is duplicated between packages/kit and packages/adapter-auto, since a little duplication is better than faffing around with a more convoluted package structure.

Closes #13528 (which has the 3.0 milestone, but this isn't a breaking change so we can do it immediately)

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.